Automatic aftercall directory and phonebook entry advertising

ABSTRACT

This disclosure provides methods, services, and platforms that automatically prompt mobile phone users to add contact information to their phone book after a triggering event such as calling a phone number. The methods, services, and platforms allow mobile network operators to provide a service that allows businesses to potentially have their numbers added to the phonebook of a mobile phone after a disconnected call.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/156,723, filed May 4, 2015. The entire contents of thatapplication are incorporated herein by reference.

BACKGROUND

Advertising has long been an effective way to communicate with existingcustomers and to attract new consumers. With the advent of mobile phonetechnology, companies and big brands have begun to redistributeadvertising dollars traditionally spent on print, TV, and internet in aneffort to reach audiences via a more personal mechanism: specifically,via a mobile device, often a device that is always with consumers. Formobile consumers with smartphones able to download applications, manybrands opt to promote products and services within an application, oftenreferred to as in-app advertising. These could consist of banner adsdisplayed at the bottom or side of the screen, or integrated within theapplication itself. Push text messaging is another mechanism commonlyused in the mobile advertising realm. With this method, consumers cansign-up to receive push messages from specific brands. In some scenariosa consumer may choose to receive advertisements from a wide variety ofcompanies in exchange for discounted cell service voice, SMS, and datausage. In some regions, push SMS marketing is heavily used regardless ofwhether consumers have explicitly opted-in to received messages fromcompanies or brands. In each case, companies are limited in the amountof information that can be provided to mobile consumers, and often SMSadvertising messages are ignored or lost in an array of other textmessages received. Even if a significant sale or coupon is provided,unless the advertisement is actionable, it is generally forgottenthereby lessening the effectiveness of using mobile as a personalizedcommunication vehicle for the brand. In some regions, mobile consumerswho have been inundated with SMS marketing messages have become immuneto the messages and are essentially conditioned to ignore texts arrivingin their inbox. For mobile marketing to be effective, a trulypersonalized approach must be taken in order to deliver relevantinformation to consumers at the right time.

SUMMARY

In one aspect, this disclosure is directed to a computer-implementedmethod for automatically prompting a user to add contact information tothe user's mobile device after a call has disconnected. The methodcomprises: receiving, at a server, an indication that a call connectedfrom the user's mobile device to a first phone number has disconnected;determining, at the server, whether the first phone number matches asecond phone number stored in a database connected to the server;requesting user information when the first phone number matches a secondphone number stored in the database; receiving, at the server, userinformation, wherein the user information comprises the user's MobileStation International Subscriber Directory Number (MSISDN); preparing anadvertising message comprising contact information comprising the firstphone number and an actionable option to add the contact information tothe phonebook of the mobile device; and sending the advertising messageto the user's mobile device. The term “phonebook” is called “Contacts”for some mobile devices. As used herein, the term “phonebook is meant toencompass all phonebooks, contacts, and similar applications used forstoring and organizing contact information on mobile devices.

In some embodiments, the method further comprises receiving at theserver an indication that the user opted to add the contact informationor an indication that the user declined to add the contact information.In further embodiments, the method also comprises storing the receivedindication and the MSISDN of the mobile device.

The platforms and methods of this disclosure can also provide updates tomobile devices that have added contact information to their phone book.In some embodiments, the method comprises: receiving, at the server, anupdate to the contact information, wherein the update comprises one ormore of a web address, a street address, a social network ID, a photo, alogo, mapping coordinates, a second phone number, a fax number, an emailaddress, a photo, a video, or a description of the owner's business;preparing a communication comprising the update to the contactinformation and an actionable response option; and sending thecommunication to the mobile device wherein the communication is sent tothe mobile device if the indication indicated that the user opted to addthe contact information. In some embodiments, the method furthercomprises receiving, at the server, an second indication indicatingwhether the user opted to add the update to the contact information.

In some embodiments, the user information further comprises thedestination address. In some embodiments, the user information furthercomprises the date and time of the call.

In some embodiments, the method comprises determining whether thematched phone number has an existing advertising campaign. This helps tomake sure an advertising campaign is still active or relevant.

In some embodiments, the method also comprises determining whether theuser has opted out of receiving an advertising message, the determiningstep comprising comparing the MSISDN of the mobile device to a databaseconnected to the server, wherein the database comprising MSISDNs thathave opted out of receiving an advertising message.

In some embodiments, the advertising message is formatted to be openedby an application on the user's mobile device. When the message isreceived on the mobile device, it triggers the launch of theapplication.

In some embodiments, the advertising message is formatted as an SMSmessage.

In some embodiments, the method further comprises determining the numberof advertising messages the MSISDN has received. In still furtherembodiments, the method also comprises determining whether the number ofadvertising messages the MSISDN has received exceeds a limit. In certainembodiments, the method also comprises determining the number ofadvertising messages the user has received in a specific time period. Inyet further embodiments, the method comprises determining whether thenumber of advertising messages the MSISDN has received exceeds a limit.

In certain embodiments, the user information further comprises the typeof mobile device.

In some embodiments, the contact information further comprises the nameof the owner of the phone number. In some embodiments, the contactinformation further comprises at least one of a web address, a streetaddress, a social network ID, a photo, a logo, mapping coordinates, asecond phone number, a fax number, an email address, a photo, a video,or a description of a business.

In another aspect, this disclosure provides a computer-implementedmethod for automatically prompting a user to add contact information tothe user's mobile phone, the method comprising: receiving, at theprocessor in the mobile phone, an indication that a call connectedbetween the mobile phone and a first phone number has disconnected;receiving at the mobile device an advertising message comprising anactionable option to add contact information to the mobile phone'sphonebook, wherein the contact information comprises the first phonenumber; and displaying on the screen the advertising message.

In some embodiments, the method further comprises receiving, at theprocessor in the mobile phone, an indication that the user desires toadd the contact information to the mobile phone's phonebook; and addingthe contact information to the mobile phone's phonebook.

In certain embodiments, the method comprises playing an alert tone onthe mobile device when the advertising message is displayed.

In some embodiments, the method further comprises receiving, at theprocessor of the mobile device, a second advertising message comprisingan actionable option to add an update to the contact information,wherein the update comprises one of a web address, a street address, asocial network ID, a photo, a logo, mapping coordinates, a second phonenumber, a fax number, an email address, a photo, a video, or adescription of a business.

In certain embodiments, the method also comprises launching anapplication installed on the mobile phone, wherein the applicationcauses the advertising message to be displayed. In some embodiments, theapplication causes the mobile phone to play a tone when the advertisingmessage is displayed. In further embodiments, the application isinstalled on the SIM card. In still other embodiments, the applicationis installed on the operating system of the mobile phone.

In some embodiments, the contact information further comprises the nameof the owner of the phone number. In certain embodiments, the contactinformation further comprises at least one of a web address, a streetaddress, a social network ID, a photo, a logo, mapping coordinates, asecond phone number, a fax number, an email address, a photo, a video,or a description of a business.

DESCRIPTION OF THE FIGURES

FIG. 1 is a graphical overview illustrating the user interface by whicha user may add a phone number directly into his or her mobile phonebookvia an interactive prompt.

FIG. 2 is a flowchart illustrating the basic architecture of theAdXecutive platform.

FIG. 3 is a flowchart illustrating the steps related to a phone callevent that will lead to the eventual triggering of the AdXecutiveservice.

FIG. 4 is a flowchart illustrating the Mobile Operator Network as itwould interact with the AdXecutive server platform.

FIG. 5 is a flowchart illustrating the exemplary process of the logicthe AdXecutive platform uses to determine if a campaign message shouldbe sent to a specific targeted mobile subscriber.

FIG. 6 is a flowchart illustrating the exemplary process of how theAdXecutive application is expressed and interacts with the user device,and thus the user experience.

FIG. 7 is a flowchart illustrating the exemplary process of how theAdXecutive platform logs the mobile device user's response anddetermines the appropriate format for adding a phone number to a mobileuser's phonebook, based on the user's device type.

FIG. 8 is a flowchart illustrating the exemplary process of how theAdXecutive platform updates the database with subscriber preferenceresults, tracking the participation such that the MNO may modify thefrequency of campaign depending on subscriber responsiveness.

FIG. 9 is a flowchart illustrating the exemplary process of how anAdXecutive campaign is designed.

FIG. 10 is a flowchart illustrating the exemplary process of how anAdXecutive campaign can in conjunction with a Mobile Directory Service.

DETAILED DESCRIPTION

This application provides aspects and embodiments of OnePIN'sAdXecutive™ service. The term “AdXecutive” is used throughout thisapplication to refer to multiple aspects and embodiments of the methods,applications, services, systems, and platforms disclosed herein. Thename “AdXecutive” is not limited to any specific embodiment and canrefer to multiple embodiments or individual embodiments. Furthermore,other names are also used to refer to embodiments described herein.

As used herein, the terms “a” and “an” mean one or more than one.

AdXecutive allows subscribers to add important phone numbers (such asairlines, hotels, restaurants, etc.) directly into their phonebooks witha click of a button after a phone call. This approach is very attractiveto advertisers, and MNOs (Mobile Network Operators) are able to charge ahigher “per-impression” rate for these mobile phonebook advertisementsdelivered using the AdXecutive platform. Thus, AdXecutive can be used toextend an MNO's mobile advertising revenues.

The systems and methods disclosed herein enable MNOs, enterprises, andsmall businesses to deepen their relationship with consumers after phonecalls to the company. These calls could be to a business's customerservice center, sales office, technical support line, reservations line,automated help line, or any other phone line associated with thebusiness. Calls could be to mobile lines or fixed lines associated withthe business.

For brands and businesses, AdXecutive is a unique way to remain relevantwith mobile subscribers. The phonebook (or contact list) is the mostcommonly used application on a mobile consumer's device. It is thefoundation for a mobile consumer's most valued communications—nearly allSMS messages and more than 85% of phone calls made are made to friends,family, colleagues, or businesses that are within a mobile subscriber'sphonebook. If a brand or company, such as an airline, car service,restaurant, flower service, or hotel is able to reside within a mobilesubscriber's phonebook, that company often becomes the de facto choicefor consumers. Brands recognize that owning a piece of real estate in aconsumer's phonebook is a valuable asset.

AdXecutive is cloud-based service that interacts with a clientapplication residing on the phone—either as a downloadable applicationfrom an external site, within the device operating system, or within aSIM card.

AdXecutive automatically detects that a specific phone number for abusiness or enterprise was dialed by the mobile subscriber. At the endof the phone call, AdXecutive asks the mobile subscriber if he wouldlike to add the business's phone number directly into his phonebook. Ifthe user chooses “yes” the contact can be added via the AdXecutiveservice with a single click—without the subscriber having to type anyinformation into his mobile phone.

AdXecutive is used with a mobile phone and any other device that can beconfigured to make phone calls. For example, tablets and other computersthat include Skype or Google Voice can be utilized with the services.

The following example illustrates how an embodiment of AdXecutive works:Bob calls Lufthansa Airlines to make a reservation for a plane ticket.He makes the call from his mobile phone. Bob speaks with a customerservice representative at Lufthansa, and books a ticket. He ends thecall. After the phone call, Bob receives a message notification on hismobile phone. The message appears directly on his screen—and he can seethe prompt even if his phone is in a locked screen mode. The message isnot delivered to his SMS inbox where it may languish for days. It is anactionable, interactive screen displayed directly to Bob. He is asked ifhe would like to add the phone number for Lufthansa Airlines into hisphonebook. The prompt appears automatically after his phone call. Bobselects “OK” and the AdXecutive client application on the mobile deviceautomatically inserts the phone number into Bob's mobile phonebook.

In another embodiment, a silent communication is sent back to the serverwith Bob's selection, and with the TAC (Type Allocation Code) of hisdevice. With the TAC of Bob's device, the platform knows what type ofphone Bob has and can create a phonebook entry that is formattedspecific to his device type. The phonebook entry is then sent back toBob's device.

In either embodiment outlined above, the application can send a silentnotification back to the cloud server with Bob's selection. The cloud isable to track the total number of mobile subscribers per enterprisebrand (in this case Lufthansa) who have received phonebook add requestsover a given date range. The cloud also tracks the total number ofsubscribers who have given a positive response requesting that the phonenumber be added, those who have given a negative response, and the totalnumber of timeouts, meaning that the subscriber likely did not see therequest.

In some embodiments, the AdXecutive platform includes a web interfacethat enables businesses, enterprises, and marketers, to log in, anddefine a campaign. Within the campaign event, businesses or mobileoperators can enter all relevant information including, but not limitedto, the target phone number(s) that will trigger the AdXecutive promptswhen called and the timeframe during which a campaign will be relevant.Business phone numbers can be validated by the MNO and/or administratorsof the platform to prevent inappropriate use.

The user interface specifics (i.e., the actual words mobile consumerswill see) can be entered via the web interface. The business/enterpriseis also able to specify the length of time (days or hours) the campaignshould run, the days of the week when it should be executed, and timesduring the day when it is relevant (for example, 8 AM-10 PM). Thebusiness also has the opportunity to set a regional campaign, based on acalling party's area code. In this instance, the business can define acampaign where only customers in a specific geographic region (asdetermined by their mobile area code where applicable) are targeted.

In some embodiments, the AdXecutive cloud (server) is connected to amobile network operator's call switch via an Application ProgrammingInterface (API). Alternatively, in other embodiments, the cloud platformcan also be connected to the mobile operator's billing platform via anAPI, depending on the operator's network structure, the operator's HLR,or other network infrastructure that determines when a specific phonenumber is dialed. When a designated campaign number is dialed (i.e., abusiness's phone number), the API informs the AdXecutive cloud platform.The business phone number and the mobile subscriber's phone number areboth passed to the platform via the API, in addition to the date andtime.

When the cloud server receives communications via the API, the businessphone number is checked to determine which campaign should be executed(as there will be multiple campaigns for different businesses running onthe platform at the same time). The platform also checks the caller'sphone number to determine if the calling party has opted out fromreceiving advertisements for specific brands. The opt out process isexplained in further detail below.

If the calling party is not on any of the opt-out blacklists, then anappropriate campaign message is prepared based on the configurationcriteria and sent to the mobile subscriber. Here, this communication isdescribed as an SMS which triggers a remote application on the callingparty's mobile phone. This could be a binary SMS, standard text SMS, aspecialized (flash, class 1) SMS, or a class 2 SMS which the handsetpasses to a SIM card within the device. Alternatively, communicationscan occur via MMS, email, USSD, or via other web-based communicationschannels between the mobile phone and the platform.

In some embodiments, when the message is received on the calling party'smobile device, the client application displays the prompt to the caller.The user is able to select a response (e.g., Yes/No), which is then sentback to the cloud via the application. Communication back to the cloudcan be via a data channel, SMS, MMS, etc.

The above embodiments can also be implemented in a manner where a clientapplication (either on the phone or on the SIM card) is not required. AUSSD (Unstructured Supplementary Service Data) channel is opened and thecommunications between the mobile subscriber and the platform occur viaUSSD communications.

In addition to after-call techniques, campaigns can be conducted in anintelligent push manner. The AdXecutive cloud server is able to trackcalls that individual subscribers make to businesses. If a businesswould like to run a campaign at a later date, subscribers who havecalled that business in the past can be targeted. This makes the promptsto the mobile subscribers relevant, as a previous relationship with thecompany had already been established by the mobile consumer. Consumerstargeted in this manner receive a prompt, similar to that outlined inthe before mentioned embodiments. Subscribers receive a message askingthem if they would like to add a business' phone number to theirphonebook. The intelligent campaigns can be arranged to run atpredefined dates and times, and for selected groups of subscribers in aregional area based on the subscriber's area code.

Each time the subscriber receives a message from the AdXecutiveplatform, he or she has the option not to reply. The service has theintelligence to count the number of rejections and, based thereon, canask the subscriber if he or she would like to opt-out of the service ifthe service is not being used. The opt-out counters for the subscriberswho have used the service and for the subscribers who have never usedthe service can be different. For example, if the mobile subscriber(calling party) has never replied to any AdXecutive prompts, an opt-outscreen can be displayed for a set number of times he has cancelled outof the prompting screen. In this example, a counter can be set at “3” sothat, for example, after 3 (three) times the subscriber chooses not tosend a reply to the survey prompt question; the subscriber will be showna screen to opt-out of the service). If the mobile subscriber hasanswered an AdXecutive prompt in the past, but has recently cancelledout of several new prompts, this opt-out counter can be set higher—forexample to 6 (six), as this caller has exhibited past behaviorindicating that he or she is willing to respond to prompts for specificcompanies in the right scenario.

The AdXecutive platform has the ability to track and store responses ofall campaigns executed. In the event that a company, business, brand, orother entity that has previously executed a campaign via the platformchanges or enhances any of its contact information, a targeted updatecan be sent to all subscribers who previously indicated they would liketo add the business contact information into their mobile phonebooks. Inone embodiment, this can be executed as a bulk campaign. The platformrecords the device type of all subscribers with the AdXecutive remoteapplication. In the bulk campaign embodiment, the platform executes thecampaign and sends the contact information in a format that provides thebest user experience based on the device type of the subscriber.

In embodiments where the information was sent and the subscriber addedthe contact to his SIM phonebook, the server can create a commandmessage which will update the contact information in the user's SIMphonebook automatically, without any user prompt. In this embodiment, afollow-up message could be sent to the subscriber outlining that aphonebook update for a specific business was made. In an alternativeembodiment, a notification can be sent to the subscriber indicating thata particular business the user previously added into his phonebook isnow offering an update. The user has the option to accept or reject theupdate.

Benefits of AdXecutive

The AdXecutive methods and systems disclosed herein provide numerousbenefits for businesses/enterprises, MNOs, and subscribers. Some ofthose benefits include:

Benefits for Businesses

-   -   Simplicity: Establishing campaigns is a simple and        straightforward process.    -   Wide Reach: Enterprises are able to collect customer feedback        from a vast array of customers across multiple segment types.        Especially in developing areas, this is key as many survey        participants may not have access to a computer or landline phone        or physical store location (i.e., typical ways in which customer        feedback is traditionally collected). However, these customers        do have mobile phones, and can be valuable participants in the        feedback process.    -   Unique Potential for Brands and MNOs: No other service in the        market is able to unlock an advertising opportunity in the        phonebook. Brands are able to extend their relationship with        customers and make it easier for customers to interact (book        tickets, make reservations, etc.). With a Directory Service type        of approach, brands provide a unique value to their customers.    -   Easy to Use: Subscribers can easily add valuable, relevant phone        numbers to their phonebooks with a single click.        Benefits for Mobile Operators    -   Revenue Generating Service: Mobile Network Operators (MNOs) are        able to offer a differentiating service to their Business and        Enterprise customers. Enterprises pay for valuable customer        feedback, creating a significant revenue generator for MNOs, as        each customer response represents a billed event.        Benefits for the Calling Party    -   Relevance: Customers receive useful information for brands and        businesses they routinely call.    -   Interoperability: The services work across all mobile devices so        subscribers have a similar experience regardless of what type of        mobile device or tablet they are using.        AdXecutive Platform

FIG. 1 showcases the user interface a mobile consumer would see when theAdXecutive service triggers and displays a prompt to a subscriber aftera phone call. In stage 100, which occurs immediately after a phone callto a business currently running an AdXecutive campaign ends, aninteractive prompt displays, optionally accompanied by an alert tone onthe mobile device.

The text displayed to the calling party is fully configurable by thecompany or business that was called. In the example in FIG. 1, a mobileuser calls a restaurant to make a reservation. After the phone call, theuser sees an automatic, interactive prompt on her handset directly onthe screen.

In an embodiment where the mobile user interacts with the campaignmessage and chooses to add the available contact information into herphonebook, the contact will display along with other contacts as shownin stage 105.

FIG. 2 is a flowchart illustrating the basic architecture of theAdXecutive platform. In one embodiment, as depicted in FIG. 2,AdXecutive utilizes the following connectivity structure: MobileSubscriber A calls a number defined in the AdXecutive target base (“1”).The Operator Switch or HLR (Home Location Registry) are in communicationwith the AdXecutive platform (“2”). This allows for the Mobile OperatorNetwork to notify the AdXecutive platform when a specific target phonenumber is dialed. In some embodiments, a database or storage servercomprising campaign trigger events, including, e.g., phone numberscalled, calls placed from specific phone numbers, etc. In someembodiments, the database or storage server is part of the MNO network.In such embodiments, the MNO network notifies the AdXecutive server thata targeted phone number has been called or has placed a call. In someembodiments, the trigger event could also be navigation to or away froma specific web address on the mobile device. In some embodiments, theAPI provides the subscribers MSISDN and the called number. In suchembodiments, the AdXecutive platform processes this information anddetermines which advertising campaign should be run. In someembodiments, the MNO network informs the AdXecutive server whichadvertising campaign should be triggered.

After a target phone number is dialed, and, subsequently, the requiredinformation necessary to trigger a campaign is passed to the AdXecutiveplatform via an API, the platform processes the information and preparesa campaign message to be sent to a mobile subscriber.

In one embodiment, the AdXecutive platform is connected to a MobileNetwork Operator SMSC (Short Message Service Center) via an SMPP (ShortMessage Peer-to-Peer) connection (“3”). Other connection types in otherembodiments are also possible. In some embodiments, the platform mayalso be connected to an MNO's MMSC (MultiMedia Message Service Center).The Operator SMSC forwards the AdXecutive campaign message to SubscriberA's device (“4”).

The phonebook promotion appears on Subscriber A's device as exemplifiedin FIG. 1, at which point the subscriber selects his or her preferredoption.

The AdXecutive remote application within Subscriber A's mobile deviceforwards the response to a designated short code at the Operator SMSC(“5”). The Operator SMSC receives and forwards the response to theAdXecutive platform (e.g., via a binary SMS message) (“6”). The platformparses the message and determines an appropriate response to SubscriberA based on Subscriber A's device type and interest in the campaignpromotion.

In the instance where Subscriber A chose to add the contact informationpromoted via the AdXecutive service, the platform would send a messageback to the subscriber in either a specially formatted vCard SMS, abinary SMS, or an MIMS. These messages would flow through the MNOs SMSCand MMSC respectively (“7”). The Operator SMSC forwards the contactinformation to the device user “(8)”.

FIG. 3 is a flowchart illustrating the steps related to a phone callevent that will lead to the eventual triggering of the AdXecutiveservice. In stage 305, Mike makes a call to a business using his mobilephone. In this example, the business is Pizza Hut, but he could bemaking a call to any type of business or individual party. In stage 310,the call connects. A connected call can have a multitude of scenarios.In this embodiment, Mike speaks with a live human when the callconnects. In other embodiments, Mike may interact with an automatedvoice response system, or may connect to a recorded message or voicemail system. In all cases, the call will end as signified by stage 315.At this point, the call is disconnected and communications between theAdXecutive platform (server) and the Mobile Operator's Networkcontinues, as outlined in FIG. 4.

FIG. 4 is a flowchart illustrating the interaction between the MobileOperator network and the AdXecutive server platform. In stage 405,Mike's call is disconnected. The Call Disconnect is a formal eventrecognized by the Mobile Operator Network. This can be a callerinitiated Call Disconnect, meaning Mike ended the call on his mobiledevice first. In some embodiments, the Call Disconnect may be a NetworkOriginated Call Disconnect Event, meaning the called party terminatesthe call or the network is not able to maintain the call and the calldrops.

When the call ends, the MNO Network will automatically check the phonenumber dialed to determine if it is a number with an AdXecutive campaignassociated with it. In some embodiments, this information is storedwithin a database in the Mobile Operator's Network. In otherembodiments, the information can be stored within the AdXecutiveplatform with regular communications between the MNO network and theAdXecutive platform via web services or APIs (Application ProgrammingInterfaces). In some embodiments the MNO network informs the AdXecutiveplatform which campaign should be triggered. In other embodiments, theAdXecutive platform determines which campaign should be triggered basedon the information received from the MNO network (e.g., the MSISDN, thecalled number, etc.). In some embodiments, the phone numbers associatedwith campaigns are stored on an application on the mobile device. Theapplication on the mobile device can check to see if a called number isstored on the device. If the number matches a stored number, theapplication can trigger the campaign. In further embodiments, the MNOnetwork notifies the AdXecutive server of each phone call placed and theAdXecutive server checks each phone number called or called from to seeif a campaign should be triggered.

If the phone number Mike dialed in this embodiment does not have anAdXecutive campaign defined, then the flow ends as shown in stage 415,and no further processing continues. If the phone number called doeshave a campaign defined, then the MNO network informs the AdXecutiveplatform of the calling event as discussed herein beginning at stage420. Information to execute the advertising campaign on the AdXecutiveplatform is passed from the MNO network to the platform. Thisinformation includes the calling party's mobile MSISDN (Mobile StationInternational Subscriber Directory Number), also known as Mike's mobilephone number. In this embodiment, Mike's mobile phone number is alsoknown as the OA, or Originating Address. In some embodiments, the MNOnetwork may also provide time and date to the AdXecutive platform.

The called phone number, referred to as the DA or Destination Address,is also sent to the AdXecutive platform. This number may be a mobilephone number dialed, an international number, a landline or fixednumber, a 1-800 phone number, a 1-900 phone number, an abbreviatednumber such as those used for emergency services such as 911, ashortcode number often used in the mobile industry for Short MessageService (SMS) communications or any other number or address mechanismused for connecting two or more parties to communicate. The AdXecutiveplatform then continues processing, as outlined in FIG. 5.

FIG. 5 is a flowchart illustrating an exemplary embodiment of a processof the logic the AdXecutive platform uses to determine if a campaignmessage should be sent to a specific targeted mobile subscriber. In thisembodiments, the AdXecutive platform receives the Origination Address,Destination Address, and, optionally, other information including dateand time from the MNO network as shown in stage 505. In stage 510, theAdXecutive platform performs a check for the Destination Address (e.g.,Pizza Hut) to determine if the campaign is still relevant and,optionally, if the date and time settings fall within preconfiguredallowable ranges. The Originating Address, Mike's phone number, is alsochecked by the platform in stage 515. The platform checks to determineif Mike has opted out of receiving message notifications. In someembodiments, a mobile subscriber such as Mike may opt out of receivingany AdXecutive notification for any brand, company, or business called.In other embodiments, the platform and remote application residingwithin Mike's device are configured to allow Mike to manage whichbrands, businesses, and companies he would like to received AdXecutivenotifications from after phone calls.

In stage 515, the platform also checks to ensure that Mike has notexceeded pre-configurable counters. In this embodiment, the counterstrack the number of total AdXecutive messages Mike has received over agiven timeframe for all brands and phone numbers called. This trackingensures that Mike does not receive an over abundance of advertisingmessages in a short time period, which could lead to him opting out ofall notifications in the future. If Mike has exceeded the allowablelimit, the processing ends as outlined in stage 516. In someembodiments, this limit may be set by the user (Mike). In otherembodiments, the limit may be set by a network administrator within theMNO or may be set by an advertising agency or company managing theplatform and overall user experience. In an embodiment where Mike hasnot exceeded the predefined counter limits, an AdXecutive message isprepared by the platform and sent to the mobile subscriber at stage 520.The message sent could be a standard SMS, binary SMS, a class 2 SMSwhich will directly communication with a SIM (Subscriber IdentityModule) card within the mobile subscriber's mobile device, an MMSmessage, a USSD message, or a web message sent over an IP (InternetProtocol) network. Processing on the calling party's device then ensues,as depicted in FIG. 6.

FIG. 6 is a flowchart illustrating the exemplary process of how theAdXecutive application is expressed and interacts with the user device,and, thus, the user experience. In stage 605, the AdXecutive remoteapplication is triggered on the mobile user's device. In someembodiments, the application may play a configurable tone as shown instage 610. In some embodiments, this tone can be configured by themobile user, or by the platform administrator. The tone can also beturned off for specific subscribers, for specific campaigns, or forcertain device types. After the tone is processed and played, thecampaign text is displayed to the calling party as shown in stage 615.The text shown to a mobile user is fully configurable and can containletters, numbers, special characters and punctuation, or may containUCS2 Unicode encoded characters such as Greek, Cyrillic, or Mandarincharacters as an example. In this embodiment, Mike may see a messagesuch as:

-   -   Thank you for calling Pizza Hut! Click OK to automatically save        our phone number into your phonebook. Make is simple to order        your next pizza with our number right at your finger tips.        Saving our number is free!

In some embodiments, the message displayed in stage 615 will beactionable by the calling party, meaning Mike can make a decision as towhether or not he would like to save Pizza Hut's phone number into hismobile phonebook using the AdXecutive service. In stage 620, Mike makesthe decision. If he decides to ignore the prompt, or if he selects“Cancel” or “No” as shown in Stage 620, he sees no further informationand his “No” response is automatically sent back to the AdXecutiveserver in stage 630. If Mike decides to add Pizza Hut's phone number atstage 620 and selects “OK” or “Yes,” his selection is sent back to theserver platform in stage 625. Mike's MSISDN, and, optionally, the dateand time or his response, the TAC (Type Allocation Code) of his devicetype, and/or a campaign ID associated with the Pizza Hut campaign arealso sent back to the platform. In some embodiments, the phone numbermay be added to Mike's mobile phonebook at this stage as well. In otherembodiments, further processing may take place as outlined in FIG. 7 inorder to enhance the user experience.

FIG. 7 is a flowchart illustrating an exemplary embodiment of how theAdXecutive platform logs the mobile device user's response anddetermines the appropriate format for adding a phone number to a mobileuser's phonebook, based on the user's device type. At stage 705, Mike'sselected response to the advertising campaign is received at theAdXecutive platform. In stage 710, the server processes Mike's response.At stage 715, the server determines if Mike indicated a positive ornegative response. If Mike did not wish to participate in theadvertising campaign, meaning he did not want to save the informationprovided by Pizza Hut into his phonebook, the AdXecutive server logs hisresponse for further analysis, as defined in the flows in FIG. 8. IfMike indicated he wanted the Pizza Hut information as indicated by an“OK” or “Yes” response, then the platform continues processing andchecks Mike's device type in stage 720. The platform checks if Mike hasa smartphone or other type of device that can receive a vCard, MMS,email, or other type of enhanced communication or enhanced businesscard/mobile phonebook contact entry. In the instance where Mike has sucha device, then the platform prepares an appropriately formatted message(such as an 8 bit vCard, a text vCard, an MMS message, an MMS vCardmessage) as in stage 740. These are only examples and other speciallyformatted types could be sent in other embodiments. At stage 745, themessage is sent to Mike's mobile device in an appropriate specialformat. At stage 750, the device may play a preconfigured alert tone.Mike receives a notification prompting him to add the Pizza Hutinformation into his phone book. In the embodiment where Mike has afeature phone, also considered a more basic device that does notrecognize MMS vCards or other types of enhanced phonebook communicationsas outlined in Stage 725, then the contact information can be sent ineither a standard SMS, or in a binary SMS format. In stage 730, themessage is prepared for a basic feature phone and sent to the mobilesubscriber. In the embodiment where a binary SMS is sent to the mobiledevice at stage 750, and the remote application on the device processesthe message. The device will optionally play a tone and prompt themobile subscriber with an actionable screen such as:

-   -   “Thanks for connecting with us at Pizza Hut! Click OK to confirm        adding our contact information directly into your phonebook.        You'll be able to call us, text us, an easily follow us on        Facebook!”

In one embodiment, Mike can confirm that he would like the contactinformation added. In a different embodiment, the remote application canautomatically add the Pizza Hut phone number directly into the phonebooksilently, without any further interaction from Mike.

In some embodiments, follow-up messages may be sent in either standardSMS format or in a binary flash SMS format thanking the mobile user foradding the phone number into their phonebook. These messages may containadditional coupon codes or discount information, social media links, orother advertisement information promoting the brand or company. Theplatform can be configured to send these follow-up messages only tomobile users who agreed to add contact information into theirphonebooks. The number of mobile users adding information drivesrevenues for Mobile Network Operators or platform administrators. Thus,subscriber choices and behaviors are tracked at both the remoteapplication level and at the platform level, as illustrated in the flowsin FIG. 8.

FIG. 8 is a flowchart illustrating an exemplary embodiment of how theAdXecutive platform updates the database with subscriber preferenceresults, tracking the participation such that the MNO may modify thefrequency of campaign depending on subscriber responsiveness. At stage805, the AdXecutive server database is updated with the resulting userselection from a targeted mobile subscriber. The platform looks todetermine if the mobile user responded in a positive or negative fashionat stage 810. In the instance where a mobile user chose to participatein the campaign, meaning that he selected “Yes” to add the calledbusiness's phone number into his phonebook, then the database countersfor that particular MSISDN are updated at stage 815 such that thecampaign will not trigger again if the phone number is dialed subsequenttimes. All counter settings and the number of times a particularcampaign can be seen by a specific mobile user are all defined at theplatform level and can be changed any time. In other embodiments, thesesettings can be managed by the subscriber and stored in within theremote application. In the embodiment where a subscriber chose not toparticipate, counters at the server platform are updated, as in stage820. If the counter threshold is exceeded, the mobile user may not betargeted for future campaigns for any brand or company. In otherembodiments, if counter thresholds are reached, the platform may send amessage to the user that prompts the subscriber to opt-out of futurenotifications. This ensures that subscribers who never wish toparticipate in any advertising campaigns and who are not interested inadding any type of contact information into their phonebooks are notroutinely targeted with campaigns that could lead to increased annoyancewith their mobile service provider, or even a poor perception of thebrand or company they had initially called.

FIG. 9 is a flowchart illustrating the exemplary process of how anAdXecutive campaign is designed. At stage 905, the campaign is definedwithin the server. This includes the days and times during which thecampaign will be relevant. In some embodiments, specific geographicregions can also be configured. In some embodiments, a maximum number oftargeted mobile subscribers can also be set. At stage 910, any phonenumbers called after which the campaign should trigger are defined.Next, during stage 915, the actual campaign text that will be shown to acalling party is defined. In stage 920, the information that will besent to the mobile user to add into a mobile phonebook is defined. Thisinformation can include the business or brand name, the phone number orphone numbers, a website address, a physical address, social media sitessuch as Facebook, Twitter, Instagram, and Snapchat, and any othercontact information or communication platform the company wishes toshare with consumers in order to continue their extended outreach.

In stage 925, configurable counters and rules for the campaign are set.In one embodiment, this could include the number of times a specificunique mobile subscriber, as defined by his MSISDN, is prompted to addcontact information into his phonebook after dialing a business phonenumber.

In other embodiments, the remote application can store target phonenumbers for advertising campaigns. In this instance, the trigger phonenumbers (such as Pizza Hut's phone number) are stored within the remotedevice application. There is no need for direct linkages between the MNOnetwork and the AdXecutive platform.

In still another embodiment, the AdXecutive platform could be used toenhance a directory service. In this scenario, as outlined in FIG. 10, amobile subscriber calls a directory service (such as “411”). The userrequests information, which could include a phone number or physicaladdress for a business or residence. In one embodiment, after therequested information is provided, the Directory Service asks the mobileuser if he would like to add the phone number directly into his mobilephonebook. The user can respond either verbally or via a menu selection.The MNO network informs the AdXecutive platform that a specific MSISDNrequires an AdXecutive campaign. The MSISDN, time, date, and phonenumber to be added to the mobile phonebook are all passed to theAdXecutive platform. A campaign is automatically triggered as outlinedin FIGS. 5, 6, and 7.

In another embodiment, the AdXecutive platform formats messages suchthat the contact information is added directly into the mobile user'sphonebook without any further prompting or interaction required from theuser.

The invention claimed is:
 1. A computer-implemented method forautomatically sending an advertising message configured to prompt a userto add contact information of a company or business to a phonebook ofthe user's mobile device after a call to the company or business hasdisconnected, the method comprising: receiving, at a server, anindication that a call connected from the user's mobile device to afirst phone number has disconnected, wherein the server is operablyconnected to a Mobile Operator's network; determining, at the server,whether the first phone number matches a second phone number associatedwith the company or business, wherein the second phone number is storedin a database connected to the server; requesting user information whenthe first phone number matches the second phone number associated withthe company or business stored in the database; receiving, at theserver, user information, wherein the user information comprises theuser's Mobile Station International Subscriber Directory Number(MSISDN); preparing, at the server, an advertising message comprisingcontact information of the company or business comprising the firstphone number and an actionable option to add the contact information ofthe company or business to the phonebook of the mobile device; andsending, from the server, the advertising message to the user's mobiledevice.
 2. The method of claim 1, further comprising receiving at theserver an indication that the user opted to add the contact informationor an indication that the user declined to add the contact informationof the company or business.
 3. The method of claim 2, further comprisingstoring the received indication and the MSISDN of the mobile device. 4.The method of claim 3, further comprising: receiving, at the server, anupdate to the contact information of the company or business, whereinthe update comprises one or more of a web address, a street address, asocial network ID, a photo, a logo, mapping coordinates, a second phonenumber, a fax number, an email address, a photo, a video, or adescription of the company or business; preparing a communicationcomprising the update to the contact information of the company orbusiness and an actionable response option; and sending thecommunication to the mobile device wherein the communication is sent tothe mobile device if the indication indicated that the user opted to addthe contact information.
 5. The method of claim 4, further comprisingreceiving, at the server, a second indication indicating whether theuser opted to add the update to the contact information.
 6. The methodof claim 1, wherein the user information further comprises thedestination address.
 7. The method of claim 5, wherein the userinformation further comprises the date and time of the call.
 8. Themethod of claim 1, further comprising determining whether the matchedphone number has an existing advertising campaign.
 9. The method ofclaim 1, further comprising determining whether the user has opted outof receiving an advertising message, the determining step comprisingcomparing the MSISDN of the mobile device to a database connected to theserver, wherein the database comprises MSISDNs that have opted out ofreceiving an advertising message.
 10. The method of claim 1, wherein theadvertising message is formatted to be opened by an application on theuser's mobile device.
 11. The method of claim 1, wherein the advertisingmessage is formatted as an SMS message.
 12. The method of claim 1,further comprising determining the number of advertising messages theMSISDN has received.
 13. The method of claim 12, further comprisingdetermining whether the number of advertising messages the MSISDN hasreceived exceeds a limit.
 14. The method of claim 12, further comprisingdetermining the number of advertising messages the user has received ina specific time period.
 15. The method of claim 14, further comprisingdetermining whether the number of advertising messages the MSISDN hasreceived exceeds a limit.
 16. The method of claim 1, wherein the userinformation further comprises the type of mobile device.
 17. The methodof claim 1, wherein the contact information of the company or businessfurther comprises the name of the owner of the second phone number. 18.The method of claim 17, wherein the contact information of the companyor business further comprises at least one of a web address, a streetaddress, a social network ID, a photo, a logo, mapping coordinates, asecond phone number, a fax number, an email address, a photo, a video,or a description of a business.